Systems and methods for automated retrieval, processing, and distribution of cyber-threat information

ABSTRACT

Systems and methods are provided for automated retrieval, processing, and/or distribution of cyber-threat information using a cyber-threat device. Consistent with disclosed embodiments, the cyber-threat device may receive cyber-threat information in first formats from internal sources of cyber-threat information using an accessing component of the cyber-threat device. The cyber-threat device may receive cyber-threat information second formats from external sources of cyber-threat information using an accessing component of the cyber-threat device. The cyber-threat device may process the received cyber-threat information in the first formats and the second formats into a standard format using a processing component of the cyber-threat device. The cyber-threat device may provide the processed items of cyber-threat information to a distributor using a distributing component of the cyber-threat device. The cyber-threat device may automatically report information concerning the processed items of cyber-threat information to a device of a user with a reporting component of the cyber-threat device.

PRIORITY CLAIM

This application is a continuation of and claims the benefit of priorityto U.S. application Ser. No. 15/133,132, filed Apr. 19, 2016 (nowallowed), which claims priority from U.S. Provisional Patent ApplicationNo. 62/150,177 filed on Apr. 20, 2015. The disclosures of theabove-referenced applications are expressly incorporated herein byreference in their entireties.

TECHNICAL FIELD

The disclosed embodiments generally relate to computer security, andmore specifically, to the automated retrieval, processing, anddistribution of cyber-threat information.

BACKGROUND

Effective management of cyber threats requires a rapid, coordinatedresponse. Otherwise, a delayed or patchwork response may permitcyber-aggressors to compromise unprotected systems and establishfootholds to support subsequent attacks.

Communities may share cyber-threat information, permitting communitymembers to collaborate to collectively detect and defend against cyberthreats. But collective action against cyber threats may be hampered by,among other things, incompatible formats for collecting cyber-threatinformation and incompatible cyber-threat information distributionmethods. Moreover, many communities have not automated the exchange ofcyber-threat information. Such communities may instead rely onperson-to-person distribution methods such as email, listservs,websites, chatrooms, discussion threads, wilds, RSS feeds; and real-timecommunication methods such as chat programs and telephoniccommunications. But these methods of communication fail to achieve therapid response and scalability possible through automatedmachine-to-machine transmission of cyber-threat information.Unfortunately, communities implementing the automated exchange ofcyber-threat information have failed to coalesce around a singlestandardized format and method of transmission. Automated exchanges ofcyber threat information among members of these communities aretherefore restricted to other members of the same community. Thesedeficiencies prevent the widespread, automated distribution ofcyber-threat information necessary to combat increasingly sophisticatedcyber-aggressors. Thus, methods and systems are needed for automaticallyretrieving, converting, and distributing cyber-threat information.

SUMMARY

The disclosed embodiments may include, for example, methods and systemsfor collecting, processing, and distributing cyber-threat information.These methods and systems may receive cyber-threat information accordingto a plurality of protocols. The cyber-threat information may beprovided in a plurality of formats. By automating the reception,processing, and distribution of cyber-threat information across aplurality of formats, and by integrating reporting and network controlfunctionality, the disclosed methods and systems may permit rapiddetection and response to cyber threats.

The disclosed embodiments may include, for example, a method forautomated collection, dissemination, and/or reporting of cyber-threatinformation from a plurality of sources using a network device. Themethod may include receiving cyber-threat information in one or morefirst formats from at least one internal source of cyber-threatinformation using an accessing component of the cyber-threat device, andreceiving cyber-threat information in one or more second formats from atleast one external source of cyber-threat information using theaccessing component of the cyber-threat device. The method may furtherinclude processing the received cyber-threat information in the one ormore first formats and the one or more second formats into a standardformat using a processing component of the cyber-threat device. Themethod may also include providing the processed cyber-threat informationto a distributor using a distributing component of the cyber-threatdevice, and automatically reporting information concerning the processedcyber-threat information to a user device using a reporting component ofthe cyber-threat device.

In some embodiments, the at least one internal source of cyber threatmay include at least one network component of an entity system. Theaccessing component of the cyber-threat device may receive cyber-threatinformation in the one or more first formats through Application ProgramInterfaces (“APIs”) exposed by the network components. The at least onenetwork component of the entity system may comprise a plurality ofnetwork components and the one or more first formats may include aplurality of first formats. The at least one network component of anentity may include a firewall appliance, router, intrusion detectionsystem, fraud detection system, email appliance, webserver, proxyserver, or security incident and event manager. The at least one networkcomponent of an entity may include a host system providing an emailclient, antivirus software, and/or anti-malware detector. Thecyber-threat information in the one or more first formats may include awebserver log, an anti-spam log, an anti-virus log, an email deliverylog, or a system log. The plurality of first formats may include one ormore of a Common Log Format, Combined Log Format, or PST file. Theaccessing component of the cyber-threat device may implement one or moreof a web service or a file system service to receive the one or moreitems of cyber-threat information in the one or more first formats. Theimplemented web service may include one or more of JSON-WSP orSOAP-WSDL. The implemented web service may be implemented as arepresentational state transfer web service.

In certain aspects, the at least one external source of cyber-threatinformation may comprise cyber-threat information generated by one ormore of a commercial security provider, governmental regulatory agency,or governmental security agency.

In various aspects, the network device may implement the accessingcomponent using a scripting language, and the accessing component maycall libraries corresponding to the APIs exposed by the networkcomponents to receive the one or more items of cyber-threat informationin the one or more first formats.

In certain aspects, the standard format may include an extensibledescription of cyber-threat information specifying observables, context,and data markings for items of cyber-threat information. The datamarkings may include information identifying the source and informationdescribing handling restrictions for each of the items of cyber-threatinformation. The processing component of the cyber-threat device mayapply exclusion criteria to determine one or more acceptable items ofcyber-threat information from the retrieved one or more items ofcyber-threat information in the one or more first formats, and theretrieved one or more items of cyber-threat information in the one ormore second formats.

In some aspects, the distributor may expose an API for receiving theprocessed items of cyber-threat information. The distributor may receivethe processed items of cyber-threat information using a web service.

In some aspects, reporting component configuration information mayconfigure the reporting component with one or more of reporting targets,reporting criteria, and reporting frequencies. The reporting componentconfiguration information may configure the reporting component toautomatically instruct a network component of the entity system tomodify a configuration of the network component. Automaticallyinstructing one or more network components to update network componentconfigurations may include instructing an email appliance to update ablacklist.

In some embodiments, the cyber threat device may include a policy engineconfigured to specify one or more users authorized to accesscyber-threat information, cyber-threat information that may be accessed,methods of access to cyber-threat information, and permissible uses ofaccessed items of cyber-threat information. In various aspects,processing component configuration information may specify one or moreidentification criteria for cyber-threat information, and processingrules for cyber-threat information.

In some embodiments, the cyber threat device may include a displaycomponent of the cyber-threat device configured to provide instructionsfor displaying a user interface on a device of a user. The displaycomponent of the cyber-threat device may enable users withoutauthorization to directly access the network components in order toaccess cyber-threat information received from the network components.The display component of the cyber-threat device may provideinstructions to generate a user interface enabling users to configureone or more of the access component, processing component, distributingcomponent, reporting component, and policy engine. Configuring thepolicy engine using the user interface may include one or more ofmanaging policies for sources of cyber-threat information, categories ofitems of cyber-threat information, or items of cyber-threat information.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are not necessarily to scale or exhaustive. Instead,emphasis is generally placed upon illustrating the principles of theinventions described herein. The accompanying drawings, which areincorporated in and constitute a part of this specification, illustrateseveral embodiments consistent with the disclosure and together with thedescription, serve to explain the principles of the disclosure. In thedrawings:

FIG. 1 depicts a diagram illustrating an exemplary system for automatedcollection, dissemination, and/or reporting of cyber-threat information,consistent with disclosed embodiments

FIG. 2 depicts a diagram illustrating of an exemplary cyber-threatdevice according to some embodiments.

FIG. 3 depicts a schematic illustrating an exemplary system forcollecting, processing, and distributing cyber-threat information usinga cyber-threat device.

FIG. 4 depicts an exemplary memory of a cyber-threat device.

FIG. 5 depicts a schematic of an exemplary item of processedcyber-threat information, consistent with disclosed embodiments.

FIG. 6 depicts a flowchart illustrating an exemplary process forautomated collection, dissemination, and/or reporting of cyber-threatinformation from a plurality of sources.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings. Whereverconvenient, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

FIG. 1 depicts a diagram illustrating an exemplary system for automatedcollection, dissemination, and/or reporting of cyber-threat information,consistent with disclosed embodiments. The components and arrangement ofthe components described in connection with FIG. 1 may vary withoutdeparting from the scope of the disclosed embodiments. In certainembodiments, the system may include an entity system 100, a privatenetwork 110, an external network 120, a cyber-threat device 130, aninternal source 140, an external source 150, a distributor 160, and auser device 170. Entity 100 a may be associated with entity system 100.User 170 a may be associated with user device 170. In some aspects,cyber-threat device 130 may automatically retrieve cyber-threatinformation from internal source 140 using private network 110. Incertain aspects, cyber-threat device 130 may automatically retrievecyber-threat information from external source 150 using one or more ofexternal network 120 and private network 110. Cyber-threat informationmay be retrieved from external source 150 and internal source 140 usinga plurality of retrieval protocols. Retrieved cyber-threat informationmay be presented in a plurality of formats. In various aspects,cyber-threat device 130 may process retrieved cyber-threat informationinto a standard format. Cyber-threat device 130 may distribute processedcyber-threat information to distributor 160. In some embodiments,cyber-threat device 130 may retrieve cyber-threat information in astandard format from distributor 160. In some embodiments, cyber-threatdevice 130 may be configured for automatic reporting of cyber-threatinformation. In certain aspects cyber-threat device 130 mayautomatically generate reports concerning received cyber-threatinformation. Cyber-threat device 130 may automatically provide suchreports to user devices (e.g., user device 170).

Entity system 100 may comprise one or more computing systems configuredto execute software instructions stored on one or more memory devices toperform one or more operations consistent with the disclosedembodiments. In one embodiment, entity system 100 may include one ormore servers, which may be one or more computer devices configured toexecute software instructions stored in memory to perform one or moreprocesses consistent with the disclosed embodiments. For example, entitysystem 100 may include one or more memory device(s) storing data andsoftware instructions and one or more processor(s) configured to use thedata and execute the software instructions to perform server-basedfunctions and operations known to those skilled in the art. Entitysystem 100 may include one or more general purpose computers, mainframecomputers, or any combination of these types of components. In certainembodiments, entity system 100 may be configured as a particularapparatus, system, and the like based on the storage, execution, and/orimplementation of the software instructions that perform one or moreoperations consistent with the disclosed embodiments. Entity system 100may be standalone, or it may be part of a subsystem, which may be partof a larger system. For example, entity system 100 may representdistributed servers, network components, and user devices that areremotely located and communicate over a network (e.g., private network110) or a dedicated network, such as a LAN, for an entity. In certainembodiments, entity system 100 may be a system configured to provideand/or manages financial service accounts, such as a bank, credit cardcompany, brokerage firm, etc. consistent with the disclosed embodiments.

An entity 100 a associated with entity system 100 may be a private orpublic entity concerned with collecting, processing, and distributinginformation regarding cyber security threats. In some aspects, entity100 a may be a private entity, such as a financial service provider oran industry group. For example, entity 100 a may be a bank. As anadditional example, entity 100 a may be an industry group, such as theFinancial Services Information Sharing and Analysis Center (FS-ISAC). Insome aspects, entity 100 a may be public entity, such as a federal,state, or local governmental body. For example, entity 100 a may be anindependent regulatory agency, such as the Federal Deposit InsuranceCorporation (FDIC). As an additional example, entity 100 a may be anexecutive agency, such as the Department of Homeland Security (DHS).

Private network 110 may be configured to provide communications withinentity 100, consistent with disclosed embodiments. In some aspects,private network 110 may be configured to provide communications betweencyber-threat device 130, internal source 140, and user device 170, asshown in FIG. 1. Each of cyber-threat device 130, internal source 140,and user device 170 may use private network 110 to access externalnetwork 120. Private network 110 may be any type of network (includinginfrastructure) that provides communications, exchanges information,and/or facilitates the exchange of information. For example, privatenetwork 110 may comprise one or more Local Area Networks, Wide AreaNetworks, virtual networks that extend a private network over a publicnetwork, such as VPN, or other suitable connection(s).

External network 120 may be configured to provide communications betweenentity 100, external source 150, and distributor 160, as shown inFIG. 1. For example, external network 120 may be any type of network(including infrastructure) that provides communications, exchangesinformation, and/or facilitates the exchange of information betweenentity 100, external source 150, and distributor 160. For example,external network 120 may be the Internet, a Local Area Network, or othersuitable connection(s).

Cyber-threat device 130 may comprise one or more devices connected toprivate network 110 of entity system 100 for collection, dissemination,and/or reporting of cyber-threat information from a plurality ofsources. Cyber-threat device 130 may include, but is not limited to, oneor more general purpose computers, servers, network appliances,mainframe computers, or any combination of these types of components.Cyber-threat information may concern unauthorized attempts to accesscomputer systems or information over a network (e.g., private network110, external network 120, etc.). Cyber threats may originate withinentity system 100. Cyber threats may originate remote from entity system100. Cyber threats may originate from, as a non-limiting example,insiders (e.g., individuals associated with, or constituents of, entity100 a), national governments, terrorists, criminals (e.g., industrialspies or organized criminal groups), hackers, and/or activists.

Internal source 140 may be a source of cyber-threat information withinentity system 100. Internal source 140 may generate cyber-threatinformation automatically or manually. For example, network componentsof entity system 100 may comprise automatic internal sources ofcyber-threat information. As an additional example, cyber-threat device130 may receive emails, reports, newsletters, messages, publications, orother communications provided by individuals associated with, orconstituents of, entity 100 a. These emails, reports, newsletters,messages, publications, and other communications may comprisemanually-generated internal sources of cyber-threat information.

External source 150 may be a source of cyber-threat information outsideentity system 100. External source 150 may generate cyber-threatinformation automatically or manually. For example, cyber-threat device130 may receive cyber-threat information provided by an automaticreporting service. As an additional example, cyber-threat device 130 mayreceive emails, reports, newsletters, messages, publications, or othercommunications provided by an external community sharing cyber-threatinformation. Such an external community may include, for example, amembership based community, such as FS-ISAC for financial servicesproviders, Microsoft's Active Protections Program (MAPP) for securitysoftware providers, or the Anti-Virus Information & Early Warning System(AVIEWS) for cyber security specialists. Such an external community mayalso include public communities sharing cyber-threat information, such anewsgroups, blogs, or similar communities. Communications from suchexternal community may comprise manual externals sources of cyber-threatinformation.

Distributor 160 may comprise one or more computing systems that areconfigured to execute software instructions stored on one or more memorydevices to perform one or more operations consistent with the disclosedembodiments. In one embodiment, distributor 160 may include one or moreservers, which may be one or more computer devices configured to executesoftware instructions stored in memory to perform one or more processesconsistent with the disclosed embodiments. For example, distributor 160may include one or more memory device(s) storing data and softwareinstructions and one or more processor(s) configured to use the data andexecute the software instructions to perform server-based functions andoperations known to those skilled in the art. Distributor 160 mayinclude one or more general purpose computers, mainframe computers, orany combination of these types of components. In certain embodiments,Distributor 160 may be configured as a particular apparatus, system, andthe like based on the storage, execution, and/or implementation of thesoftware instructions that perform one or more operations consistentwith the disclosed embodiments. Distributor 160 may be standalone, or itmay be part of a subsystem, which may be part of a larger system. Forexample, Distributor 160 may represent distributed servers, networkcomponents, and user devices that are remotely located and communicateover a network (e.g., external network 120) or a dedicated network, suchas a LAN, for an entity. In certain embodiments, distributor 160 may bea system configured to provide a clearinghouse for receiving anddistributing cyber-threat information. In some embodiments, distributor160 may be separate and distinct from entity system 100.

Distributor 160 may be configured to provide and receive cyber-threatinformation over a network (e.g., external network 120). Distributor 160may be configured to expose an endpoint for providing and receivingcyber-threat information. For example, distributor 160 may be configuredto expose a virtual inbox for reception of cyber-threat informationusing the endpoint. In certain aspects, the endpoint may be configuredto receive cyber-threat information provided according to atransportation protocol, such as a web services protocol. For example,the endpoint may be configured to receive cyber-threat informationprovided according to the Trusted Automated eXchange of IndicatorInformation (TAXII™) protocol. Distributor 160 may be configured tohandle cyber-threat information provided in a standard format. Incertain aspects, the standard format may be the Structured ThreatInformation eXpression (STIX™) format. Distributor 160 may be configuredto automatically process received cyber-threat information. Distributor160 may be configured to periodically import information deposited intothe virtual inbox into a database for distribution.

In certain embodiments, user device 170 may be a system that may be usedby user 170 a to communicate with other components of entity system 100.User 170 a may operate user device 170, or direct operation of userdevice 170, consistent with disclosed embodiments. In some embodiments,user 170 a may be an individual associated with, or a constituent of,entity 100 a. User device 170 may include, but is not limited to, ageneral purpose computer or mainframe or a mobile computing device. Sucha mobile computing device may include, but is not limited to, a cellphone, smart phone, personal digital assistant, tablet, or laptop. Insome embodiments, first user device 170 may be a client device ofanother component of entity system 100.

FIG. 2 depicts a diagram illustrating of an exemplary cyber-threatdevice consistent with disclosed embodiments. According to someembodiments, cyber-threat device 130 includes a processor 210, memory215, I/O interface(s) 220, and network adapter 225. These units maycommunicate with each other via bus 205, or wirelessly. The componentsshown in FIG. 2 may reside in a single device or multiple devices.

In various embodiments, processor 210 may be one or more microprocessorsor central processor units performing various methods in accordance tothe embodiment. Memory 215 may include one or more computer hard disks,random access memory, removable storage, or remote computer storage. Invarious embodiments, memory 215 stores various software programsexecuted by processor 210. I/O interfaces 220 may include keyboard, amouse, an audio input device, a touch screen, or an infrared inputinterface. Network adapter 225 enables cyber-threat device 130 toexchange information with private network 110 and with external network120. In various embodiments, network adapter 225 may include a wirelesswide area network adapter, or a local area network adapter.

FIG. 3 depicts a schematic illustrating an exemplary system forcollecting, processing, and distributing cyber-threat information usingcyber-threat device 130, consistent with disclosed embodiments. Thisschematic illustrates the flow of information between components ofcyber-threat device 130, and between cyber-threat device 130 and othercomponents of entity system 100.

In some embodiments, accessing component 320 of cyber-threat device 130may receive cyber-threat information 305. As described above withrespect to FIG. 1, cyber-threat information 305 may be received frominternal sources or external sources. In certain aspects, internalcyber-threat information 305 may be generated automatically or manually.For example, network components of entity system 100 may be configuredto automatically generate cyber-threat information 305. In certainaspects, network components of entity system 100 may include one or morefirewalls, routers, intrusion detection systems, fraud detectionsystems, email appliances (e.g., email scanners or gateways), servers(e.g., proxy servers or web servers, such as an apache webserver), andsecurity incident and event managers. In some aspects, networkcomponents of entity system 100 may include host systems, such as userdevice 170, which may automatically generate cyber-threat information305 using applications including intrusion detection systems, emailclients, antivirus/malware detectors, and/or customized reportingapplications.

In some aspects, cyber-threat information 305 generated by networkcomponents of the entity system 100 may comprise one or more log files,such as server logs (e.g., Apache webserver access logs), anti-spamlogs, anti-virus logs, email logs (e.g., IronPort textmail logs), orsystem logs. In various aspects, cyber-threat information 305 generatedby network components of the entity system 100 may comprise one or morearchives, such as quarantine files or email archives (e.g., “.pst” fileshosted on local systems). In certain aspects, cyber-threat information305 generated by network components of the entity system 100 maycomprise one or more blacklists/whitelists, audit records, and/ordirectory information.

In some embodiments, cyber-threat information 305 may be manuallygenerated by individuals associated with, or constituents of, entity 100a. As described above with reference to FIG. 1, cyber-threat device 130may receive emails, reports, newsletters, messages, publications, and/orother communications provided by individuals associated with, orconstituents of, entity 100 a. These emails, reports, newsletters,messages, publications, and/or other communications may comprisemanually-generated internal sources of cyber-threat information.

In some embodiments, cyber-threat information 305 may be received froman external source. As described above with reference to FIG. 1,cyber-threat device 130 may receive cyber-threat information provided byan automatic reporting service. As an additional example, cyber-threatdevice 130 may receive emails, reports, newsletters, messages,publications, or other communications provided by an external communitysharing cyber-threat information.

In some embodiments, cyber-threat device 130 may comprise policy engine310. Cyber-threat device 130 may be configured to store a program inmemory 215 defining policy engine 310. Cyber-threat device 130 may beconfigured to execute this program using processer 210 to implementpolicy engine 310. Cyber-threat device 130 may be configured to usepolicy engine 310 to govern access to cyber-threat information 305.Policy engine 310 may enforce policies governing access to cyber-threatinformation 305 based on policy rules and policy associations, describedin detail below with respect to FIG. 4. In certain aspects, policyassociations may indicate applicability of policy rules to sources ofthe cyber-threat information, categories of items of cyber-threatinformation, or items of cyber-threat information. In certain aspects,users (e.g., user 170 a operating device 170) may manage policies byadding, modifying, and/or deleting policy rules. In some aspects, users(e.g., user 170 a operating device 170) may manage policies by adding,modifying, and/or deleting policy associations. Policy rules and policyassociations may reflect security, confidentiality, and/or privacyconsiderations.

Policy engine 310 may be configured to apply policy rules andassociations to specify who may access cyber-threat information 305.Policy engine 310 may be configured to distinguish between providingcyber-threat information 305 to, for example, distributor 160, andproviding cyber-threat information 305 to individuals associated with,or constituents of, entity 100 a.

Policy engine 310 may be configured to apply policy rules andassociations to specify what cyber-threat information 305 may beaccessed. Policy engine 310 may be configured to distinguish betweencyber-threat information 305 originating from internal sources andcyber-threat information 305 originating from external sources. Forexample, policy engine 310 may enforce first policy rules regardingdistribution of cyber-threat information 305 originating from awebserver access log of entity system 100. Policy engine 310 may enforcesecond policy rules regarding distribution of cyber-threat information305 originating from a “.pst” file of user 170 a. Policy engine 310 mayenforce third policy rules regarding distribution of cyber-threatinformation 305 originating from a DHS threat report. Policy engine 310may be configured to distinguish between unprocessed cyber-threatinformation and processed cyber-threat information in a common format.In certain aspects, policy engine 310 may be configured to distinguishbetween types of unprocessed cyber-threat information. As a non-limitingexample, policy engine 310 may distinguish between system logs, emails,webserver logs, and/or reports. Policy engine 310 may be configured todistinguish between accessing different portions of cyber-threatinformation. For example, policy engine 310 may enforce first policyrules regarding access to the body of an email and second policy rulesregarding access to the header of the email.

Policy engine 310 may be configured to apply policy rules andassociations to specify how cyber-threat information 305 may beaccessed. Policy engine 310 may be configured to restrict access toparticular methods of access or particular devices for access. Forexample, policy engine 310 may be configured to deny access tocompromised devices. As another example, policy engine 310 may beconfigured to deny access to insecure devices, such as smartphones,computers, or other computer devices not connected to a private network(e.g., private network 110) of the entity (e.g., entity 100 a), or acomputing device lacking effective, up-to-date security software, suchas antivirus software.

Policy engine 310 may be configured to apply policy rules andassociations to specify permissible uses of cyber-threat information305. Policy engine 310 may be configured to distinguish between display,editing, and/or deleting of cyber-threat information 305. For example,policy engine 310 may enforce first policy rules governing viewingcyber-threat information 305 by constituents of entity 100 a, andenforce second policy rules governing distributing cyber-threatinformation 305 to distributor 160.

In some embodiments, cyber-threat device 130 may comprise displaycomponent 315. Cyber-threat device 130 may be configured to store aprogram in memory 215 defining display component 315. Cyber-threatdevice 130 may be configured to execute this program using processer 210to implement display component 315. Cyber-threat device 130 may beconfigured to use display component 315 to provide instructions causinga user device (e.g., user device 170) to display a customized userinterface 340. In some aspects, one or more of policy engine 310 ordisplay component 315 may impose authentication requirements on use ofcustomized user interface 340. In some embodiments, customized userinterface 340 may enable users lacking authentication to access networkcomponents (e.g., user 170 a) to access cyber-threat information 305generated by such network components.

In some embodiments, cyber-threat device 130 may comprise accessingcomponent 320. Cyber-threat device 130 may be configured to store aprogram in memory 215 defining accessing component 320. In certainaspects, the program may be written in a high level language. The highlevel language may be, for example, a scripting language. In someembodiments, the scripting language may be Python. Cyber-threat device130 may be configured to execute the program using processer 210 toimplement accessing component 320. Cyber-threat device 130 may beconfigured to use accessing component 320 to retrieve items ofcyber-threat information 305. Accessing component 320 may be configuredto store retrieved information in memory 215 associated with the system.For example, as described in further detail below with respect to FIG.4, accessing component 320 may be configured to store retrievedinformation in database of cyber-threat information 410.

In certain aspects, accessing component 320 may be configured toautomatically determine the appropriate method for retrievingcyber-threat information 305. For example, this determination may bebased on the source of the cyber-threat information 305. As a furtherexample, the source of the cyber-threat information 305 may beconfigured to publish a service description enabling the accessingcomponent 320 to determine the appropriate method for retrievingcyber-threat information 305.

In various aspects, accessing component 320 may be manually configuredwith appropriate methods for retrieving cyber-threat information 305.For example, accessing component configuration information, described indetail with respect to FIG. 4 below, may include data or instructionscausing accessing component 320 to retrieve cyber-threat information 305with an appropriate method. In various aspects, the accessing componentconfiguration information may correspond to the source of thecyber-threat information 305.

In some embodiments, accessing component 320 may be configured toretrieve cyber-threat information 305 from network components of entitysystem 100. In certain aspects, accessing component 320 may retrievecyber-threat information 305 using an application programming interface.In some aspects, accessing component 320 may use at least one webservice or file system service to retrieve cyber-threat information 305.This at least one web service or file system service may differ betweennetwork components. For example, accessing component 320 may beconfigured to retrieve cyber-threat information 305 from a first networkcomponent using a first web service implemented in JSON-WSP. As anadditional example, accessing component 320 may be configured toretrieve cyber-threat information 305 from a second network componentusing a second web service implemented in SOAP-WSDL. In various aspects,accessing component 320 may be configured to access network componentsusing web services implemented according to a representational statetransfer (REST) web service architecture. One of skill in the art wouldrecognize that numerous other web services and file system services maybe used, and that this description is not intended to be limiting.

In certain aspects, the format of cyber-threat information 305 maydiffer between network components. For example, a first networkcomponent may provide cyber-threat information 305 using JSON. As anadditional example, a second network component may provide cyber-threatinformation 305 using SOAP. As a further example, a third networkcomponent may provide cyber-threat information 305 using IMAP. One ofskill in the art would recognize that numerous other protocols may beused, and that this description is not intended to be limiting.

In certain aspects, accessing component 320 may be configured toretrieve cyber-threat information 305 directly from network componentsof entity system 100. For example, accessing component 320 may retrievewebserver access logs directly from a file exposed on a directory of awebserver. In various aspects, accessing component 320 may retrieveitems of cyber-threat information 305 indirectly from network componentsof entity system 100. For example, network components of entity system100 may be configured to provide cyber-threat information to anintermediate network component. In some aspects, this intermediatecomponent may comprise a security incident and event manager. Forexample, entity system 100 may comprises a plurality of webserversconfigured to forward access logs to a security incident and eventmanager. The security incident and event manager may collect theforwarded access logs. Security incident and event manager may generateprocessed access data from the forwarded access logs. In some aspects,accessing component 320 be configured to retrieve one or more of theforwarded access logs and the processed access data from the securityincident and event manager. As an additional example network componentsof entity system 100 may forward system logs to a security incident andevent manager. In some certain aspects, accessing component 320 beconfigured to retrieve one or more of the forwarded system logs and anyprocessed system logs from the security incident and event manager.

In some embodiments, accessing component 320 may be configured toretrieve cyber-threat information 305 from external sources 150. Incertain aspects, accessing component 320 may retrieve cyber-threatinformation 305 using an application programming interface. In someaspects, accessing component 320 may use at least one web service orfile system service to retrieve cyber-threat information 305. This atleast one web service or file system service may differ between externalsources (e.g., external source(s) 150). For example, accessing component320 may be configured to retrieve cyber-threat information 305 from afirst external source using a first web service implemented in JSON-WSP.As an additional example, accessing component 320 may be configured toretrieve cyber-threat information 305 from a second external sourceusing a second web service implemented in SOAP-WSDL. As a furtherexample, accessing component 320 may be configured to retrievecyber-threat information 305 from a third external source using a thirdweb service implemented in TAXII™. In various aspects, accessingcomponent 320 may be configured to access external sources using webservices implemented according to a representational state transfer(REST) web service architecture. One of skill in the art would recognizethat numerous other web services and file system services may be used,and that this description is not intended to be limiting.

In certain aspects, the format of cyber-threat information 305 maydiffer between external sources. For example, a first external sourcemay provide cyber-threat information 305 using JSON. As an additionalexample, a second external source may provide cyber-threat information305 using SOAP. As a further example, a third external sources mayprovide cyber-threat information 305 using STIX™. One of skill in theart would recognize that numerous other protocols may be used, and thatthis description is not intended to be limiting.

In some embodiments, accessing component 320 may be configured toreceive cyber-threat information 305 provided manually. In certainaspects, accessing component 320 may be configured to accept documentsuploaded to cyber-threat device 130. In some aspects, accessingcomponent 320 may cooperate with display component 315 to provideinstructions for user interface 340 to display interface elements forreceiving cyber-threat information 305. In various aspects, userinterface 340 may be configured to enable uploading of cyber-threatinformation 305. For example, non-limiting example, user interface 340may display a drop location and the user may drag a PDF of a DHS threatreport onto that drop location to manually provide information tocyber-threat device 130. In certain aspects, user interface 340 may beconfigured to accept the provision of URLs or IP addresses. For example,cyber-threat device 130 may be configured to access a webpage pointed toby a provided URL, and scrape the webpage for cyber-threat information305. External sources may manually provide cyber-threat information 305.Internal sources may manually provide cyber-threat information 305.

In some embodiments, cyber-threat device 130 may comprise processingcomponent 325. Cyber-threat device 130 may be configured to store aprogram in memory 215 defining processing component 325. In certainaspects, the program may be written in a high level language. The highlevel language may be, for example, a scripting language. In someembodiments, the scripting language may be Python. Cyber-threat device130 may be configured to execute the program using processer 210 toimplement processing component 325. Cyber-threat device 130 may beconfigured to use processing component 325 to process retrievedcyber-threat information 305. Processing component 325 may be configuredto process cyber-threat information 305 into a standard format. Incertain aspects, the standard format may be the format used bydistributor 160. For example, the standard format may be STIX™.

In certain aspects, processing component 325 may be configured toautomatically determine the appropriate method for processingcyber-threat information 305. For example, this determination may bebased on the format of the cyber-threat information 305. For example,processing component 325 may detect that cyber-threat information 305comprises webserver access logs in Common Log Format. Processingcomponent 325 may then implement scripts for converting webserver accesslogs in Common Log Format into indicators in STIX™.

In various aspects, processing component 325 may be manually configuredwith appropriate methods for retrieving cyber-threat information 305.For example, as described below with respect to FIG. 5, cyber-threatdevice 130 may be configured to use processing component configurationinformation 460 stored in memory 215 to control processing ofcyber-threat information 305. In some aspects, processing componentconfiguration information 460 may include data or instructions causingprocessing component 325 to process cyber-threat information 305 intothe standard format. For example, the processing component configurationinformation 460 may correspond to one or more of the source and formatof the cyber-threat information 305. In various aspects, componentconfiguration information 460 may store exclusion criteria. For example,processing component 325 may be configured to exclude all or some ofcyber-threat information 305 satisfying the stored exclusion criteria.

In some embodiments, processing component 325 may be configured togenerate processed cyber-threat information. In certain aspects, therelationship between retrieved cyber-threat information 305 andprocessed cyber-threat information may not be one-to-one. For example,processing component 325 may be configured to generate multiple items ofprocessed cyber-threat information from an item of cyber-threatinformation 305. As an additional example, processing component 325 maybe configured to generate an item of processed cyber-threat informationfrom multiple items of cyber-threat information 305. In various aspects,processed cyber-threat information may not include all information inthe cyber-threat information from which it is generated. In someaspects, processed cyber-threat information may only include portions ofcyber-threat information 305. For example, an item of processedcyber-threat information concerning an email may not include thecontents of the email. As an additional example, an item of processedcyber-threat information concerning a webserver access log in ApacheCombined Log Format may only include portions of the webserver accesslog. For example, the item of processed cyber-threat information mayonly include the IP address of the remote host and the HTTP requestheader. In some aspects, as described below with reference to FIG. 5,retrieved cyber-threat information 305 may not include informationpresent in processed cyber-threat information. For example, processedcyber-threat information may include context and data markings.

In some embodiments, cyber-threat device 130 may comprise distributingcomponent 330. Cyber-threat device 130 may be configured to store aprogram in memory 215 defining distributing component 330. In certainaspects, the program may be written in a high level language. The highlevel language may be, for example, a scripting language. In someembodiments, the scripting language may be Python. Cyber-threat device130 may be configured to execute the program using processer 210 toimplement distributing component 330. Cyber-threat device 130 may beconfigured to use distributing component 330 to distributed processedcyber-threat information 305 to distributor 160.

In certain aspects, distributing component 330 may be configured toprovide processed cyber-threat information according to a policyenforced by policy engine 310. In some aspects, distribution component330 may automatically determine the appropriate method for providingprocessed cyber-threat information to distributor 160. For example,distributing component 330 may determine an appropriate method forproviding processed cyber threats based on a service descriptionpublished by distributor 160. In various aspects, distributing component330 may be manually configured using distributing componentconfiguration information 470 as described below with respect to FIG. 4.

In certain aspects, distribution component 330 may be configured toprovide cyber-threat information 305 to distributor 160 using a webservice. The web service may be designed for the exchange ofcyber-threat information. The web service may implement anon-proprietary standard for exchanging cyber-threat information. Forexample, the web service may implement TAXII™. The web service may bemessage based. In certain aspects, the messages may be in a formatdesigned for the exchange of cyber-threat information. The messages mayimplement a non-proprietary standard for exchanging cyber-threatinformation, such as STIX™.

In certain aspects, one or more of distributing component 330 andaccessing component 320 may be configured to retrieve cyber-threatinformation 305 from distributor 160. The one or more of thedistributing component 330 and accessing component 320 may retrieve thecyber-threat information 305 from distributor 160 using a web service.The web service may be designed for the exchange of cyber-threatinformation. The web service may implement a non-proprietary standardfor exchanging cyber-threat information. For example, thenon-proprietary standard may be TAXII™. The web service may be messagebased. In certain aspects, the messages may be in a format designed forthe exchange of cyber-threat information. The messages may implement anon-proprietary standard for exchanging cyber-threat information, suchas STIX™. The one or more of distributing component 330 and accessingcomponent 320 may be configured to store some or all of the receivedcyber-threat information 305 in memory 215.

In some embodiments, cyber-threat device 130 may comprise reportingcomponent 335. Cyber-threat device 130 may be configured to store aprogram in memory 215 defining reporting component 335. In certainaspects, the program may be written in a high level language. Forexample, the high level language may be a scripting language, such asPython. Cyber-threat device 130 may be configured to execute the programusing processer 210 to implement reporting component 335. Cyber-threatdevice 130 may be configured to use reporting component 335 to reportinformation to distributor 160. In certain aspects, the information maybe cyber-threat information 305. In some aspects, the information may beprocessed cyber-threat information. Reporting component 335 may beconfigured to provide automatic content reporting capabilities. Asdescribed below with respect to FIG. 4, reporting componentconfiguration information store parameters describing automatic contentreporting.

In certain aspects, reporting component 335 may be configured to exposean API. The API may enable cyber-threat device 130 to provide data toother applications. The data may be cyber threat data. In certainaspects, cyber-threat device 130 may be configured to provide data to avisualization tool. For example, cyber-threat device 130 may providecyber threat data to a visualization tool in response to a query. Thequery may be received by cyber-threat device 130 from user device 170.The query may concern cyber-threat information (e.g., cyber threatsources; infrastructure, such as IP addresses, domain names, and mailservers; threats; or threat descriptions, such as cyber threat tactics,techniques, and procedures). In some aspects, visualization tool maycomprise an independent software module, such as Maltego™. In certainaspects, reporting component 335 may interact with display component 315to provide cyber-threat information. For example, reporting component335 may interact with display component 315 to provide instructions fordisplaying user interface 340 on user device 170.

In some embodiments, customized user interface 340 may be configured toenable users (e.g., user 170 a operating user device 170) to modify oneor more components of cyber-threat device 130. In certain aspects,customized user interface 340 may enable users to configure policyengine 310. For example, customized user interface 340 may enable users(e.g., user 170 a operating user device 170) to manage policy rules andpolicy associations.

In some embodiments, customized user interface 340 may enable users(e.g., user 170 a operating user device 170) to cause operating userdevice 170 to display one or more sources of cyber-threat informationand create, edit, or delete one or more policy rules or policyassociations for the one or more sources of cyber-threat information. Asanother example, customized user interface 340 may display relationshipsbetween sources of cyber-threat information. For example, customizeduser interface 340 may display a schematic depicting the networkcomponents of entity system 100. The schematic may display the role ofnetwork components and the flow of information between networkcomponents. In some aspects, customized user interface 340 may indicatepolicy restrictions for sources of cyber-threat information.

In certain embodiments, customized user interface 340 may enable users(e.g., user 170 a operating user device 170) to cause operating userdevice 170 to display one or more categories of cyber-threat informationand create, edit, and/or delete one or more policy rules or policyassociations for the one or more categories of cyber-threat information.Categories of items of cyber-threat information may include processedcyber-threat information in a common format and various types ofunprocessed cyber-threat information in a plurality of formats. Forexample, customized user interface 340 may display relationships betweencategories of cyber-threat information. In some aspects, customized userinterface 340 may indicate policy restrictions for categories ofcyber-threat information.

In various embodiments, customized user interface 340 may enable users(e.g., user 170 a operating user device 170) to cause operating userdevice 170 to display one or more individual items of cyber-threatinformation and create, edit, and/or delete one or more policy rules orpolicy associations for the one or more individual items of cyber-threatinformation. As another example, customized user interface 340 maydisplay relationships between individual items of cyber-threatinformation. In some aspects, customized user interface 340 may indicatepolicy restrictions for categories of cyber-threat information. Incertain embodiments, customized user interface 340 may enable managementof policy rules and policy associations concerning combinations of twoor more of sources of cyber-threat information, categories cyber-threatinformation, and individual items cyber-threat information.

In certain aspects, customized user interface 340 may enable users toconfigure accessing component 320. For example, user 170 a may interactwith customized user interface 340 on user device 170 to add, modify,and/or delete accessing component configuration information. Forexample, authentication credentials may be added, modified, and/ordeleted using customized user interface 340. In some embodiments,customized user interface 340 may enable users (e.g., user 170 aoperating user device 170) to configure processing component 325. Forexample, user 170 a may interact with customized user interface 340 onuser device 170 to add, modify, and/or delete processing componentconfiguration information. In some embodiments, customized userinterface 340 may enable users (e.g., user 170 a operating user device170) to configure distributing component 330. For example, user 170 amay interact with customized user interface 340 on user device 170 toadd, modify, and/or delete distributing component configurationinformation. In some embodiments, customized user interface 340 mayenable users (e.g., user 170 a operating user device 170) to configurereporting component 335. For example, user 170 a may interact withcustomized user interface 340 on user device 170 to add, modify, and/ordelete reporting component configuration information.

In some embodiments, communications channel 350 may enable components ofcyber-threat device 130 to interact and share information.Communications channel 350 may be realized as a logical structure insoftware. Communications channel 350 may be described by a programstored in memory 215. Cyber-threat device 130 may implementcommunications channel 350 by executing the program stored in memory215. This description of communications channel 350 is not intended tobe limiting, one of skill in the art would recognize many ways ofimplementing communications channel 350 to enable components ofcyber-threat device 130 to interact and share information.

The above description of cyber-threat device 130 is not intended to belimiting. One of skill in the art would recognize that multiplearchitectures may be used to implement the disclosed subject matter. Forexample, cyber-threat device 130 may combine, divide, add, and/or removeone or more of the policy engine and the accessing, processing,distributing, reporting, and displaying components, consistent withdisclosed embodiments.

FIG. 4 depicts an exemplary memory 215 of cyber-threat device 130,consistent with disclosed embodiments. As discussed above with respectto FIG. 2, memory 215 may comprise multiple devices, or a single device.For example, memory 215 may comprise a single logical memory physicallylocated on multiple devices. Memory 215 may also comprise multiplelogical memories accessed consistent with disclosed embodiments.

In some embodiments, memory 215 may include cyber-threat informationdatabase 410. Cyber-threat information database may store cyber-threatinformation received by cyber-threat device. As a non-limiting example,cyber-threat information database 410 may be implemented as ahierarchical database, relational database, object-oriented database,document-oriented database, graph-oriented database, or key-valuedatabase. One of skill in the art would recognize that many suitabledatabase implementations are possible. Cyber-threat information databasemay store processed cyber-threat information 412. Cyber-threatinformation database may store unprocessed cyber-threat information 414.In some aspects, processed cyber-threat information 412 may be stored ina logically distinct portion of cyber-threat information database 410.In certain aspects, processed cyber-threat information 412 andunprocessed cyber-threat information 412 may be stored in the samelogical portion of cyber-threat information database 410.

In some embodiments, processed cyber-threat information 412 may bestored in a standard format. The standard format may be designed forstoring cyber-threat information. The standard format may be STIX™. Insome embodiments, unprocessed cyber-threat information 412 may be storedin a plurality of formats. The plurality of formats may correspond tothe sources of cyber-threat information. For example, web server accesslogs may be stored as text files. As an additional example, local emailarchives may be stored as “.pst” files. As a further example, DHS threatreports may be stored as PDF files. Some unprocessed cyber-threatinformation 412 may be stored in an intermediate format, different fromthe format in which the cyber-threat information was received. Forexample, cyber-threat device 130 may flatten HTML-formatted email andstore the resulting text files. As another example, cyber-threat device130 may store portions of the resulting text files, such as headerinformation and hashes of email attachments.

In some embodiments, memory 215 may be configured to store libraries420. Components of cyber-threat device 130 may use libraries 420 toextend functionality, consistent with disclosed embodiments. In someaspects, components of cyber-threat device 130 may use libraries 420 toretrieve provide cyber threat data 305 from one or more of internalsource 140, external source 150, distributor 160, and/or user device170. In various aspects, components of cyber-threat device 130 may uselibraries 420 to provide cyber threat data 305 to one or more ofinternal source 140, distributor 160, and/or user device 170. In someaspects, components of cyber-threat device 130 may use libraries toprocess cyber threat data 305 into processed cyber threat data 414. Forexample processing component 325 may access libraries 420 forfunctionality to convert to or from a standard threat expression format,such as STIX™, CAPEC, IDMEF, IODEF, OpenIOC, Oval, MAEC, Veris, or Yara.Libraries may be written in a plurality of computer languages. As anon-limiting example, libraries may include a Taxii™ library (e.g.,libtaxii), a Pig workflow library, a Lipstick visualization library, anFS file system library, a RESTful API library, a JSON library, a STIX™library (e.g., python-stix). This description is not intended to belimiting: other additional or alternative libraries providing convenientfunctionality would be envisioned by one of skill in the art.

In some embodiments, memory 215 may be configured to store programs 430.As described with reference to FIG. 3, the components of cyber-threatdevice 130 may be described by one or more programs. Cyber-threat device130 may execute the one or more programs to implement the components ofcyber-threat device. In some aspects, the one or more programs maycomprise a single program. In certain aspects, the one or more programsmay be stored in memory 215.

In some embodiments, cyber-threat device 130 may be configured to storepolicy engine configuration information 440 in memory 215. As describedwith reference to FIG. 3 above, policy engine 310 may enforce a policyaccording to policy rules. Cyber-threat device 103 may store policyrules 442 as data or instructions in policy engine configurationinformation 440. Cyber-threat device 103 may store policy associations444 as data or instructions in policy engine configuration information440. Policy engine 310 may apply policy rules 442 according to policyassociations 444. In certain aspects, policy associations 444 mayindicate applicability of policy rules 442 to one or more ofcyber-threat information sources, categories cyber-threat information,or items of cyber-threat information. For example, a first policyassociation may associate a first policy rule with first web servers, asecond rule with a second webservers, and a third rule with a subset ofemail accounts on an email appliance. As a further example, policyengine configuration information 440 may store a first policyassociation linking a policy rule prohibiting distribution to intrusionattempts detected by an intrusion detection system on private network110 of entity system 100.

In some embodiments, cyber-threat device 130 may be configured to storeaccessing component configuration information 450 as data orinstructions in memory 215. In certain aspects, accessing componentconfiguration information 450 may configure accessing component 320 tocall one or more of libraries 420 to access sources of cyber-threatinformation, such as external source 150 and internal source 140. Insome aspects, accessing component configuration information 450 mayinclude network component authentication credentials 452. Authenticationcredentials 452 may comprise data or instructions for authenticatingaccess to sources of cyber-threat information. For example,authentication credentials 452 may include credentials for accessing oneor more of internal source 140, external source 150, and distributor160. As an additional example, authentication credentials 452 mayinclude credentials for accessing network components of entity network100. Credentials may include usernames, passwords, authenticationtokens, or other data or instructions supporting authentication as knownby one of skill in the art.

In some embodiments, cyber-threat device 130 may be configured to storeprocessing component configuration information 460 as data orinstructions in memory 215. Consistent with disclosed embodiments,processing component configuration information 460 may specifyidentification criteria for processing cyber-threat information. Forexample, processing component configuration information 460 may specifyhow relevant portions of unprocessed cyber-threat information 414 may beidentified and processed. In certain aspects, processing component 325may be configured to call libraries 420 according to the processingcomponent configuration information 460. In certain aspects, processingcomponent configuration information 460 may configure processingcomponent 325 to convert unprocessed cyber-threat information 414 to orfrom standard threat expression formats, such as STIX™, CAPEC, IDMEF,IODEF, OpenIOC, Oval, MAEC, Veris, and Yara. In certain aspects,cyber-threat device 130 may be configured to store exclusion criteria462 as data or instructions in processing component configurationinformation 460. Exclusion criteria 462 may include instructionspreventing processing component 325 from processing duplicateinformation. Exclusion criteria 462 may include instructions preventingprocessing component 325 from processing cyber-threat information withcertain characteristics. For example, exclusion criteria 462 mayconfigure processing component 325 to exclude information associatedwith one or more of entity 100 a and entity system 100 from processing.As an additional example, exclusion criteria 462 may configureprocessing component 325 to exclude from processing IP addresses ofentity system 100, or URLs pointing to resources on entity system 100.

In some embodiments, cyber-threat device 130 may be configured to storedistribution component configuration information 470 as data orinstructions in memory 215. Consistent with disclosed embodiments,distribution component configuration information 470 may configuredistribution component 330 to call one or more libraries to distributeprocessed cyber-threat information 412. For example, distributioncomponent configuration information 470 may configure distributingcomponent 330 to call a library to handle web services routines forcommunicating with distributor 160. As and additional example,distribution component configuration information 470 may configuredistributing component 330 to call a TAXII™ library, such as libtaxii,to handle generation, transmission, and/or reception of TAXII™ messages.

In some embodiments, cyber-threat device 130 may be configured to storereporting component configuration information 480 as data orinstructions in memory 215. Reporting component configurationinformation 480 may configure an API exposed by cyber-threat device 130for use with a visualization tool. In certain aspects, automaticreporting configurations 482 may be stored as data or instructions incomponent configuration information 480. In certain aspects, automaticreporting configurations 482 may configure reporting component 335 toautomatically generate reports. Reporting component 335 may beconfigured to provide automatically generated reports to users (e.g.,users 170 a).

Reporting targets may be stored as data or instructions in automaticreporting configurations 482. Reporting targets may specify recipientsof automatically generated reports. In some aspects, reporting targetsmay specify divisions of entity 100 a. For example, reporting targetsmay specify a Security Intelligence Center of the entity 100 a as therecipient of an automatically generated report. As an additionalexample, reporting targets may specify individuals associated with, orconstituents of, entity 100 a as recipients of an automaticallygenerated report. In various aspects, reporting targets may specifynetwork components of entity system 100 as recipients of automaticallygenerated reports.

Reporting component 335 may be configured to provide automaticallygenerated reports in response to an event. In certain aspects, one ormore automatic reporting criteria may be stored as data or instructionsin automatic reporting configurations 482. Reporting component 335 maybe configured to automatically generate a report upon satisfaction ofone or more of the automatic reporting criteria. In certain aspects,automatic reporting criteria may concern cyber-threat information. Forexample, reporting component 335 may be configured to generate reportsupon receipt of cyber-threat information 305 satisfying automaticreporting criteria. As an additional example, receipt of a predeterminednumber of emails containing computer viruses within a predetermined timemay satisfy automatic reporting criteria, causing reporting component335 to automatically generate and provide a report according toautomatic reporting configurations 482. For example, receipt of 800emails containing a particular computer virus in a day may causereporting component 335 to automatically generate and provide a reportdetailing the virus to a Security Intelligence Center of the entity 100a.

Reporting component 335 may be configured to periodically provideautomatically generated reports. One or more automatic reportingfrequencies may be stored as data or instructions in automatic reportingconfigurations 482. The automatic reporting frequencies may correspondto reports that may be automatically generated. For example, reportingcomponent 335 may be configured to generate a daily, weekly, and/ormonthly report detailing attempted intrusions into entity system 100.

In various aspects, associated actions 484 may be stored as data orinstructions in component configuration information 480. In certainaspects, associated actions 484 may configure reporting component 335 toautomatically provide instructions to network components of entitysystem 100. In some aspects, network components of entity system 100 maybe configured to automatically update the configuration of entity system100 based on the automatically provided instructions. For example,reporting component 335 may be configured to automatically instructemail appliances to update email server blacklists. Reporting component335 may be configured to provide such instructions periodically.Reporting component 335 may be configured to provide such instructionsin response to an event, such as satisfaction of automatic reportingcriteria. In certain aspects, system may require user confirmation toimplement automatic instructions.

The above description is not intended to be limiting. One of ordinaryskill in the art would appreciate that aspects of the disclosedembodiments may be implemented in a variety of ways. For example, theabove-referenced components of memory 215 may be combined, divided,omitted, and/or modified without departing from the envisioned scope ofthe disclosed embodiments. In some aspects, memory 215 may compriseadditional elements for performing the disclosed embodiments,

FIG. 5 depicts a schematic of an exemplary item of processedcyber-threat information, consistent with disclosed embodiments. Incertain aspects, item of processed cyber-threat information 510 may bestored in a standard format. This standard format may provide anextensible description of cyber-threat information. As a non-limitingexample, the standard format may support taxonomies of attack patterns,for describing and characterizing security incidents, behaviors, andartifacts. Consistent with disclosed embodiments, the standard formatmay be STIX™. In some embodiments, the standard format may be CAPEC,IDMEF, IODEF, OpenIOC, Oval, MAEC, Veris, or Yara. The above-referencedselection of standard formats is not intended to be limiting, as wouldbe recognized by one of skill in the art.

The standardized format may specify observables 512, consistent withdisclosed embodiments. Observables 512 may comprise standardizeddescriptions of artifacts or events. In some aspects, observables 512may satisfy a schema for the specification, capture, characterization,and communication of events or stateful properties that are observablein the operational domain. For example, observables 512 may include IPaddresses, domain names, file names, or email information. Emailinformation may include header information. Header information mayinclude, for example, one or more of routing information; sender,recipient, date and subject; time stamps; and/or mail transfer agentinformation. In some aspects, observables may be implemented as Cyboxelements.

The standardized format may specify context 514, consistent withdisclosed embodiments. Context 514 may comprise information identifyingthe cyber-threat information. In some aspects, the identification may begenerated by a cryptographic hash function. For example, the identifiermay be generated by an MD5 hash function. As an additional example, theidentifier may be generated by an SHA hash function. In certain aspects,the standardized format may specify that the context 514 is associatedwith the observables. For example, the context 514 may be bundled withthe observables. Consistent with disclosed embodiments, context 514 maycomprise additional information describing the cyber threat. Forexample, additional information may describe cyber threat sources; cyberthreat incidents (e.g., discrete instances of cyber threats); cyberthreat targets; tactics, tools, and procedures used by cyber threatsources; high-level descriptions of collections of related cyber threats(e.g., campaigns prosecuted by cyber threat sources); detectionprocedures for cyber threats; and/or remediation procedures for cyberthreats. One of skill in the art would recognize that this informationis not intended to be limiting, and that other types of information maybe included, consistent with disclosed embodiments.

The standardized format may specify data marking 516, consistent withdisclosed embodiments. In some aspects, data marking 516 may includeinformation producer tags. Information producer tags may identify thesource of the information. In various aspects, data marking 516 mayinclude handling restrictions. Handling restrictions may include, forexample, one or more of transfer restrictions and expirationinformation. In certain aspects, data marking 516 may implement aTraffic Light Protocol. The Traffic Light Protocol may categorizeprocessed cyber-threat information by level of restrictions on transfer.For example, red level data may be the most highly restricted, amberlevel data may be less restricted than red level data, green level datamay be even less restricted than amber level data, and white level datamay be unrestricted. As an additional example, red level processedcyber-threat information may not be provided to distributor 160, amberlevel processed cyber-threat information may be distributed only totrusted partnering entities, green level processed cyber-threatinformation may generally be shared with relevant entities, and whitelevel processed cyber-threat information may be provided to the press orpublic.

FIG. 6 depicts a flowchart illustrating an exemplary process forautomated collection, dissemination, and/or reporting of cyber-threatinformation from a plurality of sources, consistent with disclosedembodiments. Consistent with disclosed embodiments, in steps 602, 604,and 606, cyber-threat device 130 may use accessing component 320 toretrieve cyber-threat information. As described above with respect toFIG. 4, accessing component configuration information 450 may configureaccessing component 320. For example, accessing component configurationinformation 450 may configure accessing component 320 withauthentication credentials 452 necessary to retrieve cyber-threatinformation. As an additional example, accessing component configurationinformation 450 may configure accessing component 320 to use anappropriate method for retrieving cyber-threat information. In step 602,accessing component 320 may use a web service of file system service toretrieve cyber-threat information from network components of entitynetwork 100. In step 604, accessing component 320 may receiveinformation provided manually by individual or constituent of theentity. For example, accessing component 320 may be configured toprovide functionality for uploading documents containing cyber-threatinformation 305 for processing. As a further example, accessingcomponent 320 may be configured to accept URLs or IP addresses uploadedto the system. Accessing component 320, or processing component 325, maybe configured to scrape resources or web pages indicated by the providedURLs or IP addresses for cyber-threat information. In step 606,accessing component 320 may retrieve cyber-threat information 305 froman external source 150. In some aspects, accessing component 320 mayimplement at least one web service for retrieving information fromexternal sources. In step 608, one or more of accessing component 230and distributing component 330 may receive cyber-threat information fromdistributor 160. In certain aspects, cyber-threat device 130 may beconfigured to use distribution component 330 to receive cyber-threatinformation 305 from distributor 160. The cyber-threat device 130 may beconfigured to store some or all of the received cyber-threat informationin memory. For example, cyber-threat device 130 may be configured tostore unprocessed cyber-threat information in database of cyber-threatinformation 410.

Consistent with disclosed embodiments, in step 610, cyber-threat device130 may be configured to use processing component 325 to convertcyber-threat information 305. In some aspects, processing componentconfiguration information 460 may configure processing component 325,enabling processing component 325 to convert cyber-threat information305. In some aspects, processing component configuration information 460may configure processing component 325 to exclude cyber-threatinformation 305 meeting exclusion criteria 462. For example, processingcomponent 325 may be configured to exclude IP addresses of the entitysystem 100. In certain aspects, processing component 325 may convertcyber-threat information 305 to a standard format. For example,processing component 325 may convert cyber-threat information 305 to anon-proprietary format for exchanging cyber-threat information. As anadditional example, processing component 325 may convert cyber-threatinformation 305 to a format providing an extensible description ofcyber-threat information. In some aspects, the extensible format mayspecify observables, context, and data markings for the processedcyber-threat information. In some embodiments, processing component 325may convert cyber-threat information 325 to a STIX™ format. In certainembodiments, processing component 325 may convert cyber-threatinformation 325 to CAPEC, IDMEF, TODEF, OpenIOC, Oval, MAEC, Veris, orYara. Processing component 325 may generate processed cyber-threatinformation, consistent with disclosed embodiments. In some aspects, anitem of processed cyber-threat information may be generated frommultiple items of unprocessed cyber-threat information. In certainaspects, multiple items of processed cyber-threat information may begenerated from an item of unprocessed cyber-threat information. Aprocessed item of cyber-threat information may not include informationincluded in the one or more items of cyber-threat information from whichit is generated.

Consistent with disclosed embodiments, in step 622, cyber-threat device130 may be configured to use distributing component 325 to provideprocessed item of cyber-threat information to distributor 160. Asdescribed above with reference to FIG. 3, cyber-threat device 130 may beconfigured to provide processed cyber-threat information to distributor160 in accordance with a policy enforced by policy engine 310.Distributor 160 may be distinct from entity 100 a. Distributor 160 maybe a clearinghouse for distributing cyber-threat information.Distributor 160 may expose an endpoint for receiving cyber-threatinformation. In certain aspects, the endpoint may be exposed overexternal network 120.

Consistent with disclosed embodiments, in step 624, cyber-threat device130 may be configured to store processed item of cyber-threatinformation in memory 215. Cyber-threat device 130 may be configured touse one of more of accessing component 320, processing component 325, ordistribution component 330, to store processed information in memory215. Cyber-threat device 130 may be configured to store unprocessedcyber-threat information in database of cyber-threat information 410.

Consistent with disclosed embodiments, in step 632, cyber-threat device130 may be configured to use reporting component 335 to generate areport describing cyber-threat information. In some aspects, the reportmay describe processed cyber-threat information. In certain aspects, thereport may describe unprocessed cyber-threat information. In someembodiments, reporting component configuration information 480 mayconfigure reporting component 335. For example, as described above withrespect to FIG. 4, automatic reporting configuration information 482 mayconfigure the targets, frequency, and criteria for automaticallygenerated reports. In certain aspects, reporting component 335 mayinteract with displaying component 315 to provide instructions to userdevice 170 to display a user interface 340 for displaying the report.

Consistent with disclosed embodiments, in step 634, reporting component335 may expose an API for providing data in response to a query. Incertain aspects, a user (e.g., user 170 a operating user device 170) mayinteract with a visualization tool or data analytics tool implemented onuser device 170 to query the cyber-threat device 130 using the exposedAPI. Reporting component 335 may be configured to provide, in responseto this query, cyber-threat information. For example, reportingcomponent 335 may provide processed cyber-threat information. As anadditional example, reporting component 335 may provide unprocessedcyber-threat information. As a further example, reporting component 335may provide information regarding cyber threat sources; infrastructure,such as IP addresses, domain names, and mail servers; threats; andthreat descriptions, such as indicators and tactics, techniques, andprocedures. In some embodiments, reporting component 335 may providesummary or analyzed cyber-threat information, such as statisticalinformation regarding cyber threats.

Consistent with disclosed embodiments, in step 642, reporting component335 may automatically provide instructions to network components ofentity 100. In certain aspects, reporting component 335 may provideinstructions to network applications to cause them to reconfigureaspects of entity system 100. For example, reporting system 335 may beconfigured to automatically instruct email appliances to update emailserver blacklists. In some embodiments, one or more of cyber-threatdevice 130 and the instructed network component may requireauthorization to provide or implement automatic network configuration.

The sequence of steps disclosed above is not intended to be limiting. Aswould be recognized by one of skill in the art, the above-mentionedsteps may be executed in an alternative order without departing from thecontemplated embodiments. Similarly, steps may be added, omitted,combined, or divided without departing from the contemplatedembodiments.

Examples: Apache Webserver

Consistent with disclosed embodiments, accessing component 320 may beconfigured to contact an Apache webserver on entity system 100.Accessing component configuration information 452 may configureaccessing component 320 to call a FS library stored in libraries 420. FSlibrary may provide functionality for navigating the file system of theApache webserver, locating an access log file for the Apache webserver,and copying the access log file to unprocessed cyber-threat information414.

Consistent with disclosed embodiments, processing component 325 may beconfigured to retrieve the access log file for the Apache webserver fromunprocessed cyber-threat information 414 and call one of libraries 420for the functionality to process the web server log file. Processingcomponent configuration information 460 may configure processingcomponent 325 with the format of the particular Apache webserver logfile (e.g., Common Log Format). Processing component 325 may beconfigured to identify each request to the web server meetingidentification criteria specified in processing component configurationinformation 460. Processing component 325 may be configured to excluderequests satisfying exclusion criteria specified in processing componentconfiguration information 460. Processing component may be configured tocreate an item of processed cyber-threat information for each identifiedand not excluded request including the IP address for the request andthe request line provided by the remote host. Processing component maystore the processed cyber-threat information in processed cyber-threatinformation 412.

Examples: IronPort Delivery Log

Consistent with disclosed embodiments, accessing component 325 may beconfigured to contact an IronPort email appliance. Processing componentconfiguration information 460 may configure processing component 330 toretrieve a delivery log file for an IronPort email security apparatusfrom unprocessed cyber-threat information 414 and call an IronPortconversion utility to aid processing of the IronPort delivery log file.Processing component configuration information 460 may configureprocessing component 330 with the format of the IronPort delivery logfile. Processing component 330 may be configured to extract the EnvelopeFrom information from the delivery log file and identify values meetingidentification criteria specified in processing component configurationinformation 460 for processing delivery logs from this IronPort emailappliance. As a non-limiting example, processing component 325 may beconfigured to create processed cyber-threat information for each sender,including the Envelop From, Envelop to, and Source Host IP address. Theprocessed cyber-threat information may be in STIX™.

Examples: Local Email Client

Consistent with disclosed embodiments, accessing component 325 may beconfigured to contact a user device (e.g., user device 170) on privatenetwork 110 of entity system 100. Accessing component configurationinformation 450 may configure accessing component 325 to call the FSlibrary in libraries 420 for functionality to navigate the file systemof the device, and to locate a local archive of an email client (e.g.,Microsoft Outlook®, Mozilla Thunderbird®, etc.) on the user device.Accessing component configuration information 450 may configureaccessing component 325 to use MAPI/RPC to expose the header of theemail message, the body of the email message, and any attachments to theemail message. Accessing component 325 may be configured to optionallyconvert the exposed email from HTML to ASCII text. Accessing component325 may copy one or more of the header of the email message, the body ofthe email message, any attachments, and the ASCII file to unprocessedcyber-threat information 414.

Processing component 325 may be configured to retrieve one or more ofthe header of the email message, the body of the email message, anyattachments, and the ASCII file from unprocessed cyber-threatinformation 414. Processing component configuration information 460 mayconfigure processing component 325 to generate processed cyber-threatinformation. For example, processing component 325 may be configured toparse the ASCII file for IP addresses. Processing componentconfiguration information 460 may configure processing component 325 toexclude from processing IP addresses associated with entity 100 a.

Examples: DHS Threat Report

Consistent with disclosed embodiments, accessing component 325 may beconfigured to retrieve a threat report created by the Federal Bureau ofInvestigation or the Department of Homeland Security. In certainaspects, the threat report may be exposed by external source 150 using aweb service. Accessing component configuration information 450 mayconfigure accessing component 325 to retrieve the threat reportautomatically using a web service. In various aspects, the threat reportmay be uploaded using accessing component 325. Accessing component maystore the threat report in unprocessed cyber-threat information 414.

Processing component 325 may be configured to retrieve the portabledocument file from the unprocessed cyber-threat information 414.Processing component configuration information 460 may configureprocessing component 325 to call libraries 420 providing functionalitynecessary to process the item of cyber-threat information. For example,processing component 325 may call a java “.pdf” library to extractcontent from the threat report. Processing component configurationinformation 460 may specify identification criteria for processingthreat reports from the FBI or DHS. Processing component 325 may searchthe threat report according to the identification criteria using regularexpressions to extract, as a non-limiting example, IP addresses, malwarehashes, domain names, and/or URLs. Processing component configurationinformation 460 may configure processing component 325 to create one ormore processed items of cyber-threat information including, for example,an indicator for the malware comprising the hash of the malware and theassociated domain name, URL, and IP/or address.

In each of the above examples, processing component configurationinformation 460 may further configure processing component 235 toinclude data markings, such as information identifying the source foreach item of processed cyber-threat information, and handlingrestrictions. Processing component may be configured to store processedcyber-threat information in processed cyber-threat information 412.

Consistent with disclosed embodiments, distribution componentconfiguration information 470 may configure distributing component 330to automatically provide processed cyber-threat information todistributor 160. In certain aspects, distributing component 330 mayrestrict distribution of some or all of the processed cyber-threatinformation according to a policy enforced by policy engine 310.

Consistent with disclosed embodiments, reporting component configurationinformation 470 may configure reporting component 330 to automaticallyprovide processed cyber-threat information to a user device (e.g., userdevice 170). For example, reporting component 330 may generate anautomatic report to a Security Intelligence Center of entity 100 a.

Other embodiments will be apparent to those skilled in the art fromconsideration of the specification and practice of the disclosedembodiments disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the disclosed embodiments being indicated by the following claims.Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above described examples, but instead is defined by theappended claims in light of their full scope of equivalents.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

What is claimed is:
 1. A device for managing cyber-threat to an entitysystem, comprising: a network adapter configured to receive: firstcyber-threat information in a non-standard format from a networkcomponent of the entity system, the network component of the entitysystem being configured to expose an Application Program Interface (API)to collect at least a portion of the first cyber-threat information; andsecond cyber-threat information in a standard format from a distributorexternal to the entity system, the distributor being configured tocollect and share the second cyber-threat information in the standardformat; and at least one processor configured to perform operationscomprising: filtering the first cyber-threat information and the secondcyber-threat information based on exclusion criteria to exclude fromfurther processing; after completion of filtering, converting the firstcyber-threat information into processed first cyber-threat informationin the standard format, the standard format comprising: a first datamarking indicating a categorization of the first cyber-threatinformation; a second data marking indicating an expiration of the firstcyber-threat information; and a context comprising detection andremediation procedures for cyber-attacks associated with the firstcyber-threat information; combining the processed first cyber-threatinformation and the second cyber-threat information into combinedcyber-threat information; automatically instructing the networkcomponent of the entity system to reconfigure the network component inresponse to the combined cyber-threat information; and transmitting thecombined cyber-threat information to the distributor.
 2. The device ofclaim 1, wherein the operations further comprise extracting, from thecombined cyber-threat information, information identifying the combinedcyber-threat information based on stored identification criteria.
 3. Thedevice of claim 1, wherein the operations further comprise enforcingpolicy rules specifying at least one of: a user authorized to access thecombined cyber-threat information; a type of combined cyber-threatinformation that may be accessed; methods of access to the combinedcyber-threat information; or permissible uses of accessed items of thecombined cyber-threat information.
 4. The device of claim 1, wherein thenetwork adapter is further configured with a credential for accessing atleast one of an internal cyber-threat information source, an externalcyber-threat information source, or the distributor.
 5. The device ofclaim 4, wherein the credential comprises an authentication tokensupporting authentication.
 6. The device of claim 1, wherein the networkadapter is further configured to call an API library to receive thefirst cyber-threat information.
 7. The device of claim 1, wherein thenetwork component of the entity system comprises a firewall appliance,router, email appliance, webserver, or proxy server.
 8. The device ofclaim 1, wherein the standard format comprises an extensiblecyber-threat information description specifying observables and contextfor the first and second cyber-threat information.
 9. The device ofclaim 1, wherein the first data marking comprises source information andhandling restrictions for the first and second cyber-threat information.10. The device of claim 1, wherein the operations further compriseapplying the exclusion criteria to further determine acceptablecyber-threat information from the first and second cyber-threatinformation.
 11. The device of claim 1, wherein the first cyber-threatinformation comprises a blacklist to configure an email appliance. 12.The device of claim 1, further comprising an I/O interface configured todisplay a user interface on a user device.
 13. The device of claim 12,wherein the user interface is configured to receive user instructions tomodify a configuration of at least one of the network adapter, theprocessor, or the I/O interface.
 14. The device of claim 12, wherein theuser interface is configured to display flow of the first and secondcyber-threat information over the network component of the entitysystem.
 15. A device for managing cyber-threat to an entity system,comprising: a network adapter configured to receive: first cyber-threatinformation in a non-standard format from a network component of theentity system, the network component of the entity system beingconfigured to expose an Application Program Interface (API) to collectat least a portion of the first cyber-threat information; and secondcyber-threat information in a standard format from a distributorexternal to the entity system, the distributor being configured tocollect and share the second cyber-threat information in the standardformat; at least one processor configured to perform operationscomprising: filtering the first cyber-threat information and the secondcyber-threat information based on exclusion criteria to exclude fromfurther processing; after completion of filtering, converting the firstcyber-threat information into processed first cyber-threat informationin the standard format, the standard format comprising: a first datamarking indicating a categorization of the first cyber-threatinformation; a second data marking indicating an expiration of the firstcyber-threat information; and a context comprising detection andremediation procedures for cyber-attacks associated with the firstcyber-threat information; combining the processed first cyber-threatinformation and the second cyber-threat information into combinedcyber-threat information; automatically instructing the networkcomponent of the entity system to reconfigure the network component inresponse to the combined cyber-threat information; and transmitting thecombined cyber-threat information to the distributor; and anon-transitory memory configured to store the first cyber-threatinformation, the second cyber-threat information, and the combinedcyber-threat information.
 16. The device of claim 15, wherein thenon-transitory memory is further configured to store the firstcyber-threat information in the non-standard format.
 17. The device ofclaim 15, wherein the non-transitory memory is further configured tostore the combined cyber-threat information in the standard format. 18.The device of claim 15, wherein the operations further compriseautomatically generating reports to reporting targets, wherein thereporting targets are stored in the non-transitory memory.
 19. Thedevice of claim 15, wherein the network component of the entity systemcomprises a firewall appliance, router, email appliance, webserver, orproxy server.
 20. A method for managing cyber-threat to an entitysystem, comprising: receiving using a network adapter of a cyber-threatmanagement device: first cyber-threat information in a non-standardformat from a network component of the entity system, the networkcomponent of the entity system being configured to expose an ApplicationProgram Interface (API) to collect at least a portion of the firstcyber-threat information; and second cyber-threat information in astandard format from a distributor external to the entity system, thedistributor being configured to collect and share the secondcyber-threat information in the standard format; filtering, using one ormore processors of the cyber-threat management device, the firstcyber-threat information and the second cyber-threat information basedon exclusion criteria to exclude from further processing; aftercompletion of filtering, converting, using the one or more processors,the first cyber-threat information into processed first cyber-threatinformation in the standard format, the standard format comprising: afirst data marking indicating a categorization of the first cyber-threatinformation; a second data marking indicating an expiration of the firstcyber-threat information; and a context comprising detection andremediation procedures for cyber-attacks associated with the firstcyber-threat information; combining, using the one or more processors,the processed first cyber-threat information and the second cyber-threatinformation into combined cyber-threat information; automaticallyinstructing, using the one or more processors, the network component ofthe entity system to reconfigure the network component in response tothe combined cyber-threat information; and transmit, using the networkadapter of the cyber-threat management device, the combined cyber-threatinformation to the distributor; and storing to a non-transitory memorythe first cyber-threat information, the second cyber-threat information,and the combined cyber-threat information.